VM Deployment using snapshot in new zone#13178
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13178 +/- ##
============================================
- Coverage 17.67% 17.67% -0.01%
Complexity 15792 15792
============================================
Files 5922 5922
Lines 533123 533129 +6
Branches 65201 65205 +4
============================================
- Hits 94246 94242 -4
- Misses 428236 428242 +6
- Partials 10641 10645 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| } else if (templateId == null) { | ||
| throw new InvalidParameterValueException( | ||
| "Could not determine template from snapshot id=" + cmd.getSnapshotId() + | ||
| "; the source volume no longer exists. Please specify a templateId."); |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17897 |
vladimirpetrov
left a comment
There was a problem hiding this comment.
LGTM, I was able to reproduce the issue using the much easier steps, provided by @ingox:
Single zone environment, NFS and local storage pools (not sure if it's related), deploy a VM, create root volume snapshot, try to deploy a new VM using this snapshot. It fails with 'Deployment of virtual machine is supported only for Zone-wide storage pools' error message but it works fine with the patched code.
Description
This PR...
Fixes: #12443
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?